Color and style for FBD-elements determined by data type

The color/style of certain FBD-elements (e.g. value fields) are determined by the underlying →data type. Faulty FBD-elements are additionally highlighted.

Data type	Schematic representation
Data type	in legacy styling (approximate color name)	in smart styling for light and dark theme
`BOOL`	(dark shade of blue)
`BYTE, WORD, DWORD, LWORD`	(medium shade of blue)
`SINT, INT, DINT, LINT`	(shade of pink)
`USINT, UINT, UDINT, ULINT`	(shade of mauve)
`REAL, LREAL`	(shade of orange)
`TIME`	(shade of green)
`DATE, DATE_AND_TIME, TIME_OF_DAY`	(shade of khaki)
`STRING`, `CHAR`	(shade of green)
→structured data type	(shade of olive)
other complex data types, →array data type and →reference	color of the base data type Example 1: `ARRAY[1..2] OF INT` is displayed with the color of the base data type `INT`. Example 2: `REF_TO BYTE` is displayed with the color of the base data type `BYTE`.
safe data types (e.g. `SAFEBOOL`) Details: See "Highlighting safe logic in the FBD-editor".	(shade of yellow)
untyped	(shade of burgundy)

Depending on the configuration of your Neuron Power Engineer version, the FBD-editor and its elements might be displayed differently in your Neuron Power Engineer version than illustrated in the IDE documentation. This is the case, if Neuron or the system integrator has activated the smart styling or one of them has changed the styles for the FBD-editor. Subsequently, the illustration in the IDE documentation are symbolic images and the representation in your Neuron Power Engineer version takes precedence for the valid representation. In case of doubts, please contact Neuron or your system integrator.

Neuron recommends that you and/or your system integrator do not use yellow shades when designing FBD-elements because the color "Yellow" is used for tracking safe signals when developing safety-related applications. This recommendation applies in particular when you are using the legacy styling. Neuron Power Engineer does not check if colors are already used elsewhere. So the use of the yellow shades by you and/or your system integrator could have the consequence that "yellow" might also identify a non-safe logic as well.